chore: set up changesets for versioned publishing#86
Merged
Conversation
Configure @changesets/cli with public access and main as the base branch. Mark the six publishable packages (contracts, core, sdk, playwright-reporter, ai, cli) as public with explicit publishConfig while db, the apps and the shared config packages stay private. Add the release workflow that accumulates merged changesets into a version PR and publishes to npm with provenance on merge, plus CONTRIBUTING.md documenting the development flow and the changeset requirement. Verified by applying a test changeset: version bumps and changelogs were produced for public packages only, then reverted. Closes #8.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the release machinery for
@flakemetry/*npm packages.What's included
@changesets/cliwith.changeset/config.json—access: public,baseBranch: maincontracts,core,sdk,playwright-reporter,ai,cliare publishable (publishConfig.access: public);db, all apps and the shared config packages remain privaterelease.ymlworkflow: on push tomain,changesets/actionopens/updates a version PR from accumulated changesets; merging it publishes to npm with provenance (id-token: write)CONTRIBUTING.md: dev setup, branch/commit conventions, pre-PR checks, changeset requirement per published packagechangesetscriptVerification
contractsbumped0.0.0 → 0.1.0(minor) andcore→ 0.0.1(patch), both with generated changelogs; private packages untouched; artifacts reverted after the checkbuild/lint/typecheck/test→ 31/31 green,format:checkcleanBefore the first real release (not blocking)
@flakemetrynpm organizationNPM_TOKENrepository secretUntil then the workflow is inert: no pending changesets means no version PR, and publish only runs from a merged version PR.
Closes #8.